Upgrading to CCC 4.5 While Preserving Your Data
Upgrading CCC to version 4.5 introduces functional and security improvements while maintaining compatibility with supported deployment environments. To ensure a smooth upgrade and prevent unintended data loss, it is important to follow the correct upgrade path based on the version of CCC currently deployed in your environment. Data retention during the upgrade process depends on the source version. Some upgrade paths allow direct upgrades to CCC 4.5 while preserving existing data and configuration, whereas others require an intermediate upgrade step to ensure continuity. Use the table below to determine the supported upgrade path based on your currently installed version of CCC.
| Current CCC Version | Direct Upgrade to CCC 4.5 | Data Preserved | Required Action |
|---|---|---|---|
| CCC 4.4 | Yes | Yes | Follow the CCC 4.4 to 4.5 upgrade procedure |
| CCC 4.3 | Yes | Yes | Follow the CCC 4.3 to 4.5 upgrade procedure |
| Earlier than 4.3 | No | Yes | Upgrade to CCC 4.3 first, then upgrade to CCC 4.5 as explained here |
Before starting any upgrade, create a full backup of the CCC database using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.4 to CCC 4.5
This upgrade path applies to environments that are currently running CCC version 4.4. A direct upgrade from CCC 4.4 to CCC 4.5 is supported and allows existing data and configuration to be preserved when the correct procedure is followed. Before starting the upgrade, create a full backup of the CCC database using the Back up and Restore procedure explained on the Data Management page. This backup is required because the upgrade process involves removing existing containers, images, and local data directories before deploying CCC 4.5.
After the upgrade is complete, cached browser data may cause outdated information to appear in the user interface. Clear your browser cache to ensure that the latest CCC 4.5 interface and features are displayed.
Upgrading from CCC 4.4 to CCC 4.5: Podman Users
To upgrade CCC from version 4.4 to 4.5 for Podman:
Navigate to the Podman directory and stop the CCC container:
podman-compose down
Verify the removal of the CCC container:
podman ps -a
If a container named ccc appears, remove it:
podman rm -f ccc
Remove the ccc:4.4.0 image from the local repository:
podman rmi -f ccc:4.4.0
Delete the pgdata directory after verifying that a backup has been completed:
sudo rm -rf /home/ccc/pgdata
This step ensures that no residual database state from CCC 4.4 affects the CCC 4.5 startup.
Optional: Delete the server-logs directory to remove old logs:
sudo rm -rf /home/ccc/server-logs
Use sudo if required for permissions.
Load the Podman image for CCC 4.5:
podman load -i ccc-4.5.0.tar
Review and update ccc_config for CCC 4.5 compatibility:
Review and update secretfile as required:
Move secretfile to the certificates directory:
mv secretfile /home/ccc/ccc-certs
If secretfile was modified, update the CCC secret:
podman secret rm ccc_password podman secret create ccc_password secretfile
Passwords in secretfile are deleted after installation. Back up the file if you need to retain them.
Verify the secret configuration:
podman secret ls
Optional: Configure the scheduler before starting CCC.
Start the CCC container:
sh start-ccc-server.sh
Monitor the CCC logs to confirm successful startup:
podman logs -f ccc
Restore your previous data using the Back up and Restore procedure explained on the Data Management page.
Once the upgrade is complete, access CCC using one of the following URLs:
-
https://host_ip:8181 -
https://hostname:8181
Upgrading from CCC 4.4 to CCC 4.5: Kubernetes Users
To upgrade CCC from version 4.4 to 4.5 for Kubernetes:
On the master node, remove existing CCC resources:
kubectl delete -f deployment.yaml kubectl delete -f service.yaml kubectl delete -f config-map.yaml kubectl delete -f lunalogs-volume.yaml kubectl delete -f postgres-data.yaml kubectl delete -f packages-volume.yaml kubectl delete -f serverlogs-volume.yaml kubectl delete secrets ccc-password
Remove the ccc:4.4.0 image from all Worker nodes:
crictl rmi ccc:4.4.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Run the following command to determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5 image on each Worker node:
-
For
containerd, runctr -n=k8s.io images import ccc-4.5.0.tar. -
For
CRI-O, runpodman load -i ccc-4.5.0.tar.
List images to confirm successful import:
crictl images
Create the CCC secrets on the master node:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Update config-map.yaml and deployment.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f [ccc-podname]
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrading from CCC 4.4 to CCC 4.5: Helm Users
To upgrade CCC from version 4.4 to 4.5 for Helm:
On the master node, uninstall the existing CCC release and remove secrets:
helm uninstall ccc kubectl delete secrets ccc-password
Remove the ccc:4.4.0 image from all Worker nodes:
crictl rmi ccc:4.4.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5 image on each Worker node:
-
For
containerd, runctr -n=k8s.io images import ccc-4.5.0.tar. -
For
CRI-O, runpodman load -i ccc-4.5.0.tar.
Verify image availability:
crictl images
Recreate the CCC secrets:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Update values.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f [ccc-podname]
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrade from CCC 4.3 to CCC 4.5
This upgrade path applies to environments that are currently running CCC version 4.3. A direct upgrade from CCC 4.3 to CCC 4.5 is supported and allows existing data and configuration to be preserved when the upgrade is performed in the correct sequence. As part of the upgrade process, existing containers, images, and local database directories are removed before CCC 4.5 is deployed. For this reason, a full backup of the CCC database must be created before starting the upgrade by following the Back up and Restore procedure explained on the Data Management page.
After the upgrade is complete, cached browser data may cause outdated information to appear in the user interface. Clear your browser cache to ensure that the CCC 4.5 interface and features are displayed correctly.
Upgrading from CCC 4.3 to CCC 4.5: Podman Users
To upgrade CCC from version 4.3 to 4.5 for Podman:
Navigate to the Podman directory and stop the CCC container:
podman-compose down
Verify the removal of the CCC container:
podman ps -a
If a container named ccc appears, remove it:
podman rm -f ccc
Remove the ccc:4.3.0 image from the local repository:
podman rmi -f ccc:4.3.0
Delete the pgdata directory after verifying that a backup has been completed:
sudo rm -rf /home/ccc/pgdata
This step ensures that no residual database state from CCC 4.3 affects the CCC 4.5 startup.
Optional: Delete the server-logs directory to remove old logs:
sudo rm -rf /home/ccc/server-logs
Load the Podman image for CCC 4.5:
podman load -i ccc-4.5.0.tar
Review and update ccc_config for CCC 4.5 compatibility:
Review and update secretfile as required.
Verify the secret configuration:
podman secret ls
Optional: Configure the scheduler before starting CCC:
Start the CCC container:
sh start-ccc-server.sh
Monitor the CCC logs:
podman logs -f ccc
Restore your previous data using the Back up and Restore procedure explained on the Data Management page.
Once the upgrade is complete, access CCC using one of the following URLs:
https://host_ip:8181https://hostname:8181
Upgrading from CCC 4.3 to CCC 4.5: Kubernetes Users
To upgrade CCC from version 4.3 to 4.5 for Kubernetes:
On the master node, remove existing CCC resources:
kubectl delete -f deployment.yaml kubectl delete -f service.yaml kubectl delete -f config-map.yaml kubectl delete -f lunalogs-volume.yaml kubectl delete -f postgres-data.yaml kubectl delete -f packages-volume.yaml kubectl delete -f serverlogs-volume.yaml kubectl delete secrets ccc-password
Remove the ccc:4.3.0 image from all Worker nodes:
crictl rmi ccc:4.3.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5 image on each Worker node:
-
For
containerd, runctr -n=k8s.io images import ccc-4.5.0.tar. -
For
CRI-O, runpodman load -i ccc-4.5.0.tar.
List images to confirm successful import:
crictl images
Create the CCC secrets on the master node:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Update config-map.yaml and deployment.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f [ccc-podname]
Restore your data using the Back up and Restore procedure:
Upgrading from CCC 4.3 to CCC 4.5: Helm Users
To upgrade CCC from version 4.3 to 4.5 for Helm:
On the master node, uninstall the existing CCC release and remove secrets:
helm uninstall ccc kubectl delete secrets ccc-password
Remove the ccc:4.3.0 image from all Worker nodes:
crictl rmi ccc:4.3.0
Delete the pgdata directory on each Worker node:
sudo rm -rf /home/ccc/pgdata
Optional: Delete the server-logs directory:
sudo rm -rf /home/ccc/server-logs
Determine the container runtime:
crictl config --get image-endpoint
Import the CCC 4.5 image on each Worker node:
-
For
containerd, runctr -n=k8s.io images import ccc-4.5.0.tar. -
For
CRI-O, runpodman load -i ccc-4.5.0.tar.
Verify image availability:
crictl images
Recreate the CCC secrets:
kubectl create secret generic ccc-password \ --from-literal=CCC_TRUSTSTORE_PASSWORD='password' \ --from-literal=CCC_KEYSTORE_PASSWORD='password' \ --from-literal=CCC_CREDENTIALSTORE_PASSWORD='password' \ --from-literal=HSM_PASSWORD1='password' \ --from-literal=CRYPTO_OFFICER_PASSWORD='password' \ --from-literal=HSM_PASSWORD2='password' \ --from-literal=CCC_ADMIN_PASSWORD='password' \ --from-literal=CA_CERTIFICATE_PASSWORD='password' \ --from-literal=CCC_DB_PASSWORD='password'
Update values.yaml as required:
Start the CCC service:
sh start-ccc-server.sh
Monitor CCC logs:
kubectl logs -f [ccc-podname]
Restore your data using the Back up and Restore procedure explained on the Data Management page.
Upgrade from Versions Earlier Than CCC 4.3 to CCC 4.5
Direct upgrades from versions earlier than CCC 4.3 do not support data retention. To preserve existing data and configuration, an intermediate upgrade to CCC 4.3 is required before proceeding to CCC 4.5. To upgrade CCC from a version earlier than 4.3 to 4.5 while preserving data:
Back up the existing CCC database using the Back up and Restore procedure explained on the Data Management page.
Upgrade the existing CCC deployment to version 4.3 by following the CCC 4.3 Upgrade Guide.
Verify that the CCC 4.3 service starts successfully and that no startup errors are reported.
After confirming that CCC 4.3 is running correctly, create a new backup of the CCC 4.3 database using the Back up and Restore procedure described on the Data Management page.
Proceed with the upgrade from CCC 4.3 to CCC 4.5 using the procedure described earlier in this document.
